Automated service-oriented performance management

ABSTRACT

In an embodiment, a data processing method comprises creating and storing a scoring threshold value that is associated with determining whether a baseline operation rule is to be generated; receiving, from service monitoring processes, datasets of operations performed on digital objects by processors associated with computer applications; aggregating operations and identifying operation properties from the aggregated operations to generate an aggregated baseline dataset that represents operation properties from aggregated operations; assigning score values to each of the operation properties, wherein each assigned score value represents whether a particular operation property is a candidate for generating a rule that defines expected operation property values for the particular operation property; automatically generating a set of baseline operations rules for only those operation properties that have assigned values that exceed the score threshold value. The set of baseline operations rules is programmed to detect anomalous operations that contain unexpected operation property values.

BENEFIT CLAIM

This application claims the benefit under 35 U.S.C. § 120 as acontinuation of application Ser. No. 15/447,668, filed Mar. 2, 2017, theentire contents of which are hereby incorporated by reference for allpurposes as if fully set forth herein. Applicants rescind any disclaimerof subject matter of the parent application and advise the USPTO thatthe claims of this application may be broader than in the parent.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to management monitoring ofcomputer program applications and components of those applicationstermed services. The disclosure relates more specifically tocomputer-implemented techniques for automatically generating securityrules to monitor operations performed by applications and components ofthose applications.

BACKGROUND

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

Protecting computer program applications running on networked computingdevices typically involve some aspect of monitoring applications.Monitoring can involve collecting application messages and other datatraffic that the applications emit toward a network, directed at peerinstances of the applications, directed at servers, or directed atclient computing devices.

Approaches for protecting computer program applications against securitythreats can be grouped in the following categories: vulnerabilitydetection, network based approaches, and runtime access control.Vulnerability detection involves examining computer program binary filesto determine if known vulnerabilities exists. Specifically, staticvulnerability detection approaches involve scanning program executablesor virtual container images for virus signatures. One of the majordrawbacks to this approach is that virus signature definitions requirefrequent updating. Without updated virus definitions, scanning programexecutables may miss new vulnerabilities, such as zero dayvulnerabilities.

Network based approaches to identifying security threats involveexamining network traffic to detect malicious activity. However, networkbased approaches have limited visibility into application behaviorbecause specific types of application activity, such as file I/O, doesnot have any corresponding network activity to be detected at thenetwork level.

Runtime access control involves limiting the type and number of actionsthat specific computer programs can perform. Computer programsimplemented within a virtual environment such as a virtual machine orcontainer may be monitored using runtime access control.Containerization has emerged as a popular alternative to virtual machineinstances for developing computer program applications. Withcontainerization, computer program code can be developed once and thenpackaged in a container that is portable to different platforms that arecapable of managing and running the containers. Consequently,containerization permits faster software development for the sameprogram for multiple different platforms that would otherwise requireseparate source branches or forks, or at least different compilation andexecution environments. The DOCKER containerization system from Docker,Inc. of San Francisco, Calif. has emerged as a popular choice forcontainerization architecture. However, containerization also can imposeconstraints on inter-program communications.

Runtime access control includes mandatory access control techniques.Mandatory access control techniques involve operating systemsconstraining the ability of an initiator to access or perform anoperation on a target object. Examples of mandatory access controlinclude Security-Enhanced Linux (SELinux) which is a Linux kernelsecurity module that provides a mechanism for supporting access controlsecurity policies. Another example of access control involves asandboxing approach, such as seccomp, which is a security mechanism forseparating running programs and restricting the number of system callsallowed to be made from the computer program. However, runtime accesscontrol approaches have several drawbacks. One such drawback is that itrequires a manually defined set of rules for each unique programmonitored. Defining program specific rules involves customized manualinteraction and may require continuous updating when programs containchanges or version updates. Another drawback includes the high level ofmaintenance to ensure that the manually defined rules are behavingcorrectly and do not become stale or generate false positives or falsenegatives.

The term “microservices” describes a modular way to architectapplications, so that they are split into independent units (i.e.,“services”) which communicate through application programming interfaces(APIs) and well defined interfaces. Microservices bring many benefits,such as reduction of the number of points of failure; a structure thatenables multiple teams to work concurrently on the same application, andsupports continuous delivery; better separation of concern andresponsibility; and scalability.

Further information about microservices is available online at the timeof this writing in the article “Microservices” in the “wiki” folder ofthe domain “en.wikipedia.org” and the present disclosure presumes thatthe reader is knowledgeable about microservices at least to the extentset forth in the foregoing article. Microservices have been adopted bymany enterprises in the past, but we're now seeing a big push towardthem, driven by the rise of containerization technologies like Docker.

Containers offer a way to package and isolate individual applicationsand allows for finer grain access control than generally supported byexisting access control techniques such as SELinux and seccomp, whichare typically implemented to provide system level protection. Thereforea more flexible monitoring and protection system that does not requiremanually defining sets of rules is desirable.

SUMMARY

The appended claims may serve as a summary of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example computer network according to anembodiment.

FIG. 2 illustrates an example of a computing node and interactionsbetween containers, applications, and a monitoring agent within thecomputing node.

FIG. 3 illustrates an example process for automatically generating rulesto detect anomalous operations from multiple processes from multiplecomputing devices.

FIG. 4 is a block diagram that illustrates a computer system upon whichan embodiment of the invention may be implemented.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however,that the present invention may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to avoid unnecessarily obscuring thepresent invention.

In an embodiment, a data processing method provides an improvement inautomatically generating programmed rules to detect anomalous operationsin computer systems executing containerized computer programapplications. The method comprises a computer system creating andstoring, within digital data storage, a score threshold value that isassociated with determining whether to generate a baseline operationrule for detecting anomalous operations. The computer system receives,from one or more service monitoring processes that are executing on oneor more computer systems, datasets of operations that have beenperformed on digital objects by one or more processes associated withone or more computer applications executing on the one or more computersystems. Each of the datasets of operations includes a set of operationsdata representing records of operations that were performed byparticular processes associated with a particular computer applicationrunning on the one or more computer applications. The computer systemaggregates operations from the datasets of operations by groupingoperations together using common identifiers associated with theoperations and identifying operation properties from the aggregatedoperations. The computer system generates an aggregated baseline datasetthat represents operation properties identified from the aggregatedoperations. The computer system assigns score values to each of theoperation properties in the aggregated baseline dataset, where eachassigned score value represents whether a particular operation propertyis a candidate for generating a rule that defines expected operationproperty values for the particular operation property. The computersystem automatically generates a set of baseline operation rules foronly those operation properties in the aggregated baseline dataset thathave assigned values that exceed the score threshold value. Thegenerated set of baseline operation rules are programmed to detectanomalous operations that contain unexpected operation property values.Other aspects and features of various embodiments will become apparentfrom the disclosure as a whole as described in other sections herein.

1. Structural Overview

FIG. 1 illustrates an example computer data communications network thatis structured and programmed to implement one embodiment of thetechniques herein. FIG. 1 depicts a distributed monitoring systemcomprising a monitoring system 120, a plurality of computing nodes 105,110, 115, and a network 190 that communicatively couples the monitoringsystem 120 to the plurality of computing nodes 105, 110, and 115. In anembodiment, the monitoring system may represent one or more separatecomputer systems communicatively coupled and configured to receivedatasets of operations from multiple computing nodes, aggregate andscore the operations within the datasets, and generate a set of baselineoperation rules that may be used by the multiple computing nodes todetect anomalies in future operations performed by applicationsimplemented on the multiple computing nodes.

In an embodiment, the monitoring system 120 is programmed with orcomprises a communication layer 125 and a data management layer 145.“Layer,” in this context, refers to any combination of electronicdigital interface circuits, microcontrollers, firmware such as drivers,and/or computer programs or other software elements.

The communication layer 125 may be programmed or configured to performinput/output interfacing functions including receiving datasets ofoperations from the plurality of computing nodes 105, 110, 115 andsending data back to the plurality of computing nodes 105, 110, 115. Inan embodiment the datasets of operations contain records of operationsperformed on objects by applications running within containers or otherenvironments within the plurality of computing nodes 105, 110, 115. Thecommunication layer 125 may be programmed or configured to send thereceived datasets of operations to a storage repository 150 and retrievestored rules data from a rules repository 160.

The data management layer 145 may be programmed or configured to manageread operations and write operations involving the storage repository150 and the rules repository 160 and other functional elements of thesystem, including queries and result sets communicated between thefunctional elements of the system and the repository. Examples of datamanagement layer 145 include JDBC, SQL server interface code, and/orHADOOP interface code, among others. The storage repository 150 and therules repository 160 may each comprise a database. As used herein, theterm “database” may refer to either a body of data, a relationaldatabase management system (RDBMS), or to both. As used herein, adatabase may comprise any collection of data including hierarchicaldatabases, relational databases, flat file databases, object-relationaldatabases, object oriented databases, and any other structuredcollection of records or data that is stored in a computer system.Examples of RDBMS's include, but are not limited to including, ORACLE®,MYSQL, IBM® DB2, MICROSOFT® SQL SERVER, SYBASE®, and POSTGRESQLdatabases. However, any database may be used that enables the systemsand methods described herein.

In an embodiment, the monitoring system 120 contains speciallyconfigured logic including, but not limited to, operation aggregationinstructions 130, aggregated operation scoring instructions 135, andrule generation instructions 140. Each of the operation aggregationinstructions 130, the aggregated operation scoring instructions 135, andthe rule generation instructions 140 comprises executable instructionsloaded into a set of one or more pages of main memory, such as RAM, inthe monitoring system 120 which when executed cause the monitoringsystem 120 to perform the functions or operations that are describedherein. For example, the operation aggregation instructions 130 maycomprise executable instructions loaded into a set of pages in RAM thatcontain instructions which when executed cause performing aggregationfunctions on captured computer operations that are described herein. Theinstructions may be in machine executable code in the instruction set ofa CPU and may have been compiled based upon source code written in JAVA,C, C++, OBJECTIVE-C, or any other human-readable programming language orenvironment, alone or in combination with scripts in JAVASCRIPT, otherscripting languages and other programming source text. The term “pages”is intended to refer broadly to any region within main memory and thespecific terminology used in a system may vary depending on the memoryarchitecture or processor architecture. In another embodiment, each ofthe operation aggregation instructions 130, the aggregated operationscoring instructions 135, and the rule generation instructions 140 alsomay represent one or more files or projects of source code that aredigitally stored in a mass storage device such as non-volatile RAM ordisk storage, in the monitoring system 120 or a separate repositorysystem, which when compiled or interpreted cause generating executableinstructions which when executed cause the monitoring system 120 toperform the functions or operations that are described herein withreference to those modules. In other words, the drawing figure mayrepresent the manner in which programmers or software developersorganize and arrange source code for later compilation into anexecutable, or interpretation into bytecode or the equivalent, forexecution by the monitoring system 120.

The operation aggregation instructions 130 provide instructions toaggregate the received datasets of operations from the differentcomputing nodes 105, 110, and 115 and generate an aggregated baselinedataset of operation properties. The aggregated baseline dataset ofoperation properties may contain property values from similar operationsthat have been grouped together based upon common attributes. Theaggregated operation scoring instructions 135 provide instructions toassign score values to each of the property elements within theaggregated baseline dataset. In an embodiment, the assigned score valuesare used to determine whether property elements may be used to createbaseline operation rules to detect anomalous operations on the pluralityof computing nodes 105, 110, and 115. The rule generating instructions140 provide instructions to automatically generate a set of baselineoperation rules from elements in the aggregated baseline dataset thathave score values that exceed a configured score value threshold. Thebaseline operation rules may be programmed to detect future anomalousoperations performed by applications running on the plurality ofcomputing nodes 105, 110, and 115.

The network 190 broadly represents any combination of one or more datacommunication networks including local area networks, wide areanetworks, internetworks or internets, using any of wireline or wirelesslinks, including terrestrial or satellite links. The network(s) may beimplemented by any medium or mechanism that provides for the exchange ofdata between the various elements of FIG. 1. The various elements ofFIG. 1 may also have direct (wired or wireless) communications links.The monitoring system 120, the plurality of computing nodes 105, 110,and 115, and other elements of the system each comprise an interfacecompatible with the network 190 and are programmed or configured to usestandardized protocols for communication across the networks such asTCP/IP, Bluetooth, and higher-layer protocols such as HTTP, TLS, and thelike.

The plurality of computing nodes 105, 110, and 115 each representcomputer systems programmed and configured to execute one or moreapplications, virtual computer environments, virtual computer managementservices, and other computer processes. Virtual computer environmentsmay include several different types of implemented virtual machines thatvirtualize a computer operating system and the applications programmedto run on the virtual operating system. Virtual computer managementservices may include implementations of containerization services formanaging multiple containers running different applications. In anembodiment, each of the plurality of computing nodes 105, 110, and 115contain agents 107, 112, and 117 respectively. The agents 107, 112, and117 each represent a monitoring agent programmed and configured tocapture information from processes, threads, and containers running onthe plurality of computer nodes 105, 110, and 115. Records of operations109 represents an embodiment of a dataset of operations captured by theagent 107. The records of operations 109 may include sets of operationsperformed on different objects by one or more applications, processes,and threads on computing node 105. Example of objects may include, butare not limited to, files, directories, processes, pipes, networkconnections, network ports, IP and subnet endpoints, and system calls.

FIG. 2 depicts a detailed example of interactions within a computingnode between instantiated containers, applications, and an agent.

In an embodiment, the computing node 105 may be programmed andconfigured to implement one or more virtual computer managementservices. The virtual computer management services may be configured tomanage multiple containers and applications using a set of sharedcomputer resources. In an embodiment, the shared computer resources aremanaged by kernel 205. Kernel 205 may represent several different typesof operating system layers that manages the computing resources betweenthe computing node 105 and the instantiated containers and applications.Kernel module 210 represents a configured or programmed module ofcomputer instructions programmed to send and receive data between thekernel 205 and the instantiated containers and applications.

Applications 215 and 220 each represent applications that may beinstantiated directly by the kernel 205. Containers 225 and 230 eachrepresent instances of containers instantiated by the kernel 205. Eachof the containers 225 and 235 may instantiate one or more distinctapplications instances with the containers 225 and 230. Additionally,containers 225 and 235 may each represent different types of containersmanaged by different container management systems. For example,container 225 may represent a container managed by Docker that includesan instance of application 227 running within the container 225.Container 235 may represent a container managed by LXC that includes aninstance of application 237 running within container 235. In anembodiment, agent 107 communicates directly with the kernel module 210to receive different types of kernel activity occurring between thekernel 205, application 215, application 220, container 225, container235, and the computing node 105.

Each of the agents 107, 112, and 117 and the monitoring system 120 maycommunicate with each other through an API. For example, the monitoringsystem 120 may issue calls in a pre-arranged format, for example overHTTP (Hypertext Transfer Protocol), to obtain information from theagents 107, 112, and 117 related to the computing nodes 105, 110, and115, including the number or applications and containers. Alternatively,the API may be “push” based. That is, the agents 107, 112, and 117 maysend information to the monitoring system 120 without receiving a callfrom the monitoring system 120.

In an embodiment, operations detection system 170 represents amonitoring management system that may organize configuration options formonitoring computer services. The operations detection system 170 may beconfigured to manage and delegate stored operation rules for specificcomputing nodes, containers, and applications and transmit operationrules to one or more agents in order to monitor and detect operationanomalies based upon the stored operation rules. In an embodiment,operations detection system 170 may include the rule repository 160,where operation rules may be stored.

2. Functional Overview

FIG. 3 illustrates an example process for automatically generating rulesto detect anomalous operations in computer systems. FIG. 3 is a flowdiagram that is disclosed at the level of detail and using the terms ofcommunication that are customarily used by persons of the level of skillin the art to whom this disclosure is directed. FIG. 3 may be used as aplan or algorithm that serves as a basis for writing programinstructions to implement, by execution using a computer, the processrepresented in the drawing.

At step 305, a score threshold value is created and stored. The scorethreshold value is a baseline cutoff score used to determine whether abaseline operation rule is to be generated based on score values forproperty elements of operations. For example, received datasets ofoperations may be aggregated based upon operation attributes, such asoperation type or any other grouping. In this context, operation typerefers to different types of operations that may be performed ondifferent objects, such as opening an object file, connecting to anetwork port, or saving an object file. The property elements ofaggregated operations may then be scored based upon the similarity ofproperty element values such as, input, and/or output values. Based uponthe calculated score value of the property element, if the calculatedscore value is above the generated score threshold value, then abaseline operation rule may be generated that describes the expectedoutcome of the property element for that operation type.

In an embodiment, the rule generation instructions 140 provideinstructions to create a score threshold value. The score thresholdvalue may be generated based on a historical score threshold value usedto generate existing baseline operation rules and the score valuesassociated with the aggregated operations. For example, if the existingbaseline operation rules were previously successful in detectingoperation anomalies in a set of computing nodes, then the scorethreshold value for the existing baseline operation rule may be used togenerate a new set of baseline operation rules for a new set ofoperations and computing nodes. Conversely, if the existing baselineoperation rules were not successful in detecting operation anomalies,then the score threshold value may be set to a value higher than thehistorical score threshold value. In other embodiments, the scorethreshold value may be generated from input supplied by a user in theform of rule configuration parameters and user feedback used todetermine the optimal score threshold value. In yet other embodiments,the score threshold value may be based on a combination of user inputparameters and historical score threshold value data.

At step 310, the monitoring system 120 receives datasets of operationsfrom a plurality of agents 107, 112, and 117 deployed on computing nodes105, 110, and 115 respectively. In an embodiment, the agent 107 mayutilize markers within kernel source code, such as tracepoints, toinstrument different places within the operating system kernel in orderto extract activity information. For example, the kernel module 210 maybe configured with tracepoints to capture information including, but notlimited to, system calls, file system activity, disk activity, networkand socket activity, established connections, open ports, process andthread execution, and inter process communications such as pipes andmutexes. As represented in FIG. 2, the agent 107 may capture theactivity information from the kernel module 210.

In an embodiment, the agent 107 may continuously listen for the activityinformation from the kernel module 210 and store the activityinformation in one or more record tables called program tables. Theprogram tables may be configured to contain detailed or aggregatedrecords of operations performed by each process, thread, and containermonitored by the agent 107. Records, within the program table, maycontain properties describing: the operation executed; the process orprogram that executed the operations, where the program may represent anaggregation of multiple processes that run the same executable; theobject that was the target of the operation; the application withinwhich the operation was executed; and the container within which theoperation was executed. In an embodiment, records may be configured tobe stored in a specific format. For example, records within the programtable may be formatted as JavaScript Object Notation (JSON), ExtensibleMarkup Language (XML), Protocol Buffers developed by Google, or anyother data formatting standard.

In an embodiment, the agent 107 may be configured to generate multipleprogram tables, where the records of operations for each application arestored in a dedicated program table for that particular application. Forexample, a program table may be created for the application Dropbox andanother program table may be created for the application MicrosoftOutlook.

Records of operations, within the program table, may be organized intogroups based upon properties of the operations. In an embodiment,operations may be organized into groups based upon the type of objectsaccessed by the operations. For example, an operation may access aparticular file or directory. The particular file or directory may beused to organize groups of operations that access that type of file ordirectory. Different objects types may include, but are not limited to,files, directories, server ports, bound ports, IP endpoints, subnetendpoints, executed programs and system calls. Each of these objecttypes may be further organized into a hierarchy of subgroups. Forexample, operations organized by the object type “files” may besubdivided into the specific type of file accessed by the operation.Examples of subgroups of “files” include, but are not limited to,startup files and regular files. Startup files may include files thatare initially accessed by the application, such as files that areaccessed within seconds of starting the application. Regular filesinclude files that are accessed by the application during regularactivity after initialization. In an embodiment, subgroups of objecttypes may be further subdivided into smaller subgroups based onproperties of the objects within each of the subgroups. For example, thesubgroup “startup files” may be further subdivided into subgroups basedupon access permissions associated with the files. One such subgroup mayinclude all startup files that have read only access, another subgroupmay include all startup files that have read/write access, and yetanother subgroup, called “other”, may include files where permissionscould not be determined.

In an embodiment, the program table may be organized in a hierarchicalformat where the records of operations are grouped and sub-grouped in ahierarchal format. TABLE 1 in the APPENDIX illustrates an example of aprogram table formatted as JSON output.

In an embodiment, TABLE 1 is sent by the agent 107 on computing node105, via network 190, to the monitoring system 120. The communicationlayer 125 may receive multiple program tables as datasets of operationsincluding TABLE 1. In an embodiment, the communication layer 125 maystore received program tables in the storage repository 150.

In an embodiment, the communication layer 125 may also receive metadatafrom the plurality of computing nodes 105, 110, and 115 that includes,but is not limited to, host names, user tags, cloud service providerinstance tags, container names, container identifiers, container labels,container image names, container identifiers, orchestrator labels, andorchestrator annotations. The received metadata may be stored within thestorage repository 150 and may be used to group operations from multipleprogram tables based upon common identifiers and tags from theoperations. For example, the metadata may be used to identify relevantproperties from operations within different program tables based uponvarious metadata tags. Operations that have similar metadata propertiesmay then be aggregated to generate an aggregated baseline dataset ofdata that represents operations that have similar metadata properties.

At step 315 operations represented in the program tables are aggregatedto generate an aggregated baseline dataset. In an embodiment, theoperation aggregation instructions 130 provide instructions to generatean aggregated baseline dataset by grouping operations together based onproperties, identifiers, and metadata associated with the operations. Inan embodiment the aggregated baseline dataset may be represented as adata structure that contains aggregated property data from operationsgrouped together based upon their similar properties. In an embodiment,multiple aggregated baseline datasets may be generated, where eachdataset represents a group of operations grouped together by one or morecommon properties.

In an embodiment, the operation aggregation instructions 130 provideinstructions to retrieve stored metadata and the program tables storedin the storage repository 150. The stored metadata may be used as keyvalues to aggregate operations from the multiple program tables. Forexample, operations, within the multiple program tables, may be analyzedto determine which operations were executed within a container.Determining whether operations were executed within a container may bebased on whether the operations contain a container ID property value.In an embodiment, the container ID values from operations from multipleprogram tables may be cross-referenced against the stored metadata todetermine additional property values related to the container ID values.For example, container image names and other container information maybe associated with the container ID values.

Operations may be aggregated based upon a common property such as acontainer ID value for the purpose of generating an aggregated baselinedataset. In an embodiment, aggregating operations may include traversingthrough groups and sub-groups of operations, within a program table,that match a particular container ID value. During aggregation, each ofproperty values from the operations are aggregated to generate theaggregated baseline dataset. The aggregated baseline dataset may beorganized as a data structure of property types and sub-types withelements and sub-elements representing properties and sub-propertiesfrom the operations used to make up the aggregated baseline dataset. Forexample, elements may represent properties such as, files accessed,executed programs, subnet endpoints, IP endpoints, server ports,directories accessed, and bound ports. Each of the elements may alsocontain sub-elements that represent specific sub-property types for eachproperty element. For example, the element “files accessed” may includesub-elements that group files based on permission type, such assub-elements for “read only” files, “read/write” files, and “unknownpermission” files. Each element and sub-element may contain a set of oneor more values populated from the operations. The set of values maycontain duplicate values from multiple operations. For example, thelocal port element for a particular application may contain a set ofvalues as {80, 80, 80, 80}, where values extracted from each of the fouroperations are the same value for the local port element. By trackingduplicate values in the set of values, the monitoring system 120 may beable to determine, based on the number to similar values, an expectedvalue for a particular property.

In an embodiment, the aggregated baseline dataset may contain trackedvalues that track the total number of values within a set of values andthe number of distinct values in the set of values for each of theelements and sub-elements. The total number of values and the number ofdistinct values may be used to determine which property elements haveconsistent values. For example, a distinct value count may be recordedfor elements representing connections to local ports and remote ports.Local port values for the operations associated with the particularaggregated baseline dataset may be the same if the operation originatedfrom the same container and therefore the distinct values count is equalto one. Whereas remote port values for operations may contain distinctvalues as the operations may be associated to several different remotelocations, therefore the distinct value count is likely to be calculatedas a high value. As a result, each of the elements in an aggregatedbaseline dataset contains distinct value counts that may be used todetermine which elements have consistently common values and may be usedfor rule generation and which elements have distinct values and may notbe useful for rule generation.

In an embodiment, generating the aggregated baseline dataset is notlimited to determining groupings of operations based on any singlemetadata value. Combinations of metadata values may be used to determinegroups of operations. For example, container ID combined with cloudservice provider instance tags may be used to identify subsets ofoperations that contain both a common container ID and a cloud serviceprovider instance tag for generating an aggregated baseline dataset ofoperations called redis:2.8.19/US West, where the container ID isredis:2.8.19 and the cloud service provider instance tag is US West.Generating the aggregated baseline dataset based upon a combination ofmetadata values may be useful in determining consistent values relatedto a subset of operations associated with a combination of metadatavalues, which may not have been detected if operations were groupedusing only a single metadata value. TABLE 2 in the APPENDIX illustratesan example of an aggregated baseline dataset displayed in a hierarchalformat with elements and sub-elements including a distinct value count.

At step 320, score values are assigned to elements in the aggregatedbaseline dataset. In an embodiment, the aggregated operation scoringinstructions 135 provide instruction to assign score values to elementsin the aggregated baseline dataset. The score value for a particularelement represents whether the property element is suitable forgenerating a rule for detecting anomalies based on the property elementvalues. In this context, the rule represents the expected propertyvalues for similar operations. If an operation generates a propertyvalue that is not consistent with expected property values in thedefined rule, then the operation may be deemed as an anomalousoperation.

In an embodiment, a high score value for a particular property elementrepresents that the property element contains consistent values that maybe candidates for generating rules to identify anomalies. For example,if the local port for Dropbox operations is consistently either 80 or443, then a rule may be generated for detecting anomalies in Dropboxoperations when the local port is any value other than 80 or 443.Conversely, property element values for a property element that containsseveral unique values may indicate that the property element is not agood candidate for rule generation since observed values from operationsfluctuate between several different values.

In an embodiment, the aggregated operation scoring instructions 135provide instruction to calculate score values for the aggregatedbaseline dataset based upon the distinct value count associated witheach property element value. As discussed in step 315, the distinctvalue count tracks the number of unique values identified for eachproperty element. Using distinct value counts, each of the propertyelements within an aggregated baseline dataset may be scored todetermine which property elements should be used for rule creation. Ascore value for a property element may be calculated using the totalnumber of values in the set of values for the property element, thenumber of distinct values based on the distinct value count for theproperty element, and determining the number of duplicate values that donot match other values within the set of values. Based upon the totalnumber of values and the number of duplicate values, a baseline ofexpected values may be determined. For example, if the set of values fora local port contains {80, 80, 443, 80, 443, 443, and 355}, then it maybe determined based on the number of duplicates for values 80 and 443that both values 80 and 443 are baseline expected values and the value355 is a value that does not match the other baseline values.

In an embodiment, score values may be calculated using a ratio of thetotal number of values within the set of values and the number of valuesthat do not match the baseline values. The following pseudocode providesan example of calculating a score value:

-   -   entrycnt=<number of values, within the set of values, for the        element>    -   newcnt=<number of values, within the set of values, whose        content does not match the expected baseline values>        score_ns=int((1.0−float(newcnt/entrycnt)*100))        where score_ns is a calculated score value on a scale of 0 to        100 and is based upon the ratio of values that make up the        expected baseline values.

In an embodiment, the calculated score value may be updated whenadditional operation data is received from the plurality of computingnodes 105, 110, and 115 respectively. For example, if additionaloperations are added to an existing aggregated baseline, then an updatedscore value may be calculated by updating the total entrycnt, the newcntif the new values do not match expected baseline values, andrecalculating the score_ns based on the updated entrycnt and newcnt. Inanother embodiment, the calculated score values may be updated from userfeedback received from one or more monitoring agents such as agent 107.

The calculated score value may be adjusted based upon the total numberof values that make up the set of values for an element. For example, ifthe set of values used to calculate the score value is low, then theratio of unexpected values over total number of values may beunnecessarily skewed by the low total value count. In an embodiment, thecalculated score value may be adjusted using a smoothing function thatadjusts the calculated score value based upon the total number of valueswithin the set of values. The following pseudocode provides an exampleof a smoothing function that modifies the score value to take intoaccount the total number of values used to determine the score value:score=min(Analyzer.time_smooth(score_ns,entrycnt,100),score_ns)where “score” equals an adjusted score that is the minimum value of theoriginally calculated score_ns and an adjusted score_ns value when thesmoothing function is applied. Embodiments of the smoothing function mayinclude any type of mathematical adjustment factor that may reduce thescore_ns value based upon the total number of values used to calculatethe score_ns.

In an embodiment, protection functions may be implemented that ensurethat calculated score values are not purposefully skewed by any one typeof operation or any set of operations that originate from a singlesource. In one example, a large number of identical operations may skewthe values for a particular element. If the large number of identicaloperations originated from a single source, either purposefully orcoincidentally, then the single source may influence the score valuecalculation and in turn influence rule generation based upon the skewedscore value. Score value calculation may be configured to minimize asingle user or type of operation in order prevent certain operationsfrom skewing the set of calculated score values. In an embodiment, scorevalue calculation for an element may include generating separate scorevalues for the element based upon the user ID associated with eachoperation. By calculating scores based on the element and the user ID,large numbers of operations from a single user may not influence aparticular score value for the element. The score value for theparticular element may then be calculated as an aggregate of calculatedscore values from each user ID from the set of operations. In anotherembodiment, each user ID may be assigned its own score value for theelement, thereby eliminating score value influence from other users.

In an embodiment, the calculated scores for elements and sub-elementsmay be stored within the aggregated baseline dataset. For example, ifthe aggregated baseline dataset is represented as a data hierarchalstructure with elements and sub-elements, then the calculated score foreach element may be stored within a score property value within eachelement.

Referring back to FIG. 3, at step 325 the rule generation instructions140 determine whether elements within the set of aggregated baselinesmay be used for generating a rule. In an embodiment, one or moreproperty values from elements may be used to generate an operation ruleif the calculated score values for the elements exceeds the stored scorethreshold value from step 305. For example, if the stored scorethreshold value is 85 out of 100 and a calculated score value for aparticular element is 90 out of 100, then the property values within theparticular element may be used to generate a rule that describesexpected property values for the particular element for new operations.In an embodiment, the rule generation instructions 140 provideinstructions to evaluate all elements that have calculated score valueswithin the aggregated baseline to determine which elements andsub-elements may be used for rule generation. If a calculated scorevalue for an element is below the score threshold value then the elementwill not be used for rule generation and the monitoring system 120 willcontinue to evaluate the remaining property elements within theaggregated baseline dataset.

At step 330, the rule generation instructions 140 provide instruction toautomatically generate a set of baseline operation rules based upon theelements in the aggregated baseline dataset that have calculated scorevalues that exceed the stored score threshold value. In an embodiment,one or more rules may be generated from the elements within theaggregate baseline dataset. For example, elements that represent regularfile reads and local connected ports may have calculated score valuesthat exceed the stored score threshold value and may be used to generateone or more rules for expected operations. One such rule may be based onthe expected property values in the regular file reads elements. Forinstance, if the expected property values include file-A and file-B thatare read during operations within the particular aggregated baselinedataset, then a regular file read rule may be generated that specifiesthat only file-A and file-B are expected files to be read duringperformance of the particular operation. If during an operation governedby the regular file read rule performs a file read on another file, suchas file-C, then the regular file read rule may be used to determine thatthe operation performed was an anomalous operation. Similarly, a localconnected ports rule may be generated using the expected property valuesfrom the local connected ports element.

In an embodiment, one or more elements may be combined to create acombination rule based on properties from the one or more elements.Using the previous example, a file read-local connected port combinationrule may be generated that specifies new operations are valid if theoperation properties values for file reads and local connected portsfall within the defined value ranges for file reads and local connectedports as defined in the file read-local connected port combination rule.If either a file is read that is not defined in the file read-localconnected port combination rule or a local port is connected to that isnot defined in the file read-local connected port combination rule, thenthe operation may be interpreted as being an anomalous operation.

In an embodiment, baseline operation rules generated may includespecific template definitions that may be configured to incorporatecustomized rules that are based upon initialization parameters specificto the application and container being monitored. For example, atinitialization, a specific container may specify certain inputparameters for TCP ports or definition files to be used. The baselineoperation rule may be configured to define allowable TCP ports anddefinition files used during initialization. By generating baselineoperation rules based upon template definitions, the baseline operationrules may be customized to each container and application based upon theconfiguration options defined with configuration files for eachcontainer.

In an embodiment, the set of baseline operation rules for the aggregatedbaseline dataset may be stored within the rules repository 160 for useby the operations detection system 170. The operations detection system170 represents a rules enforcement system that may organize and delegateoperation rules for specific computing nodes, containers, andapplications to one or more agents in order to monitor and detectoperation anomalies based upon the generated rules. In an embodiment,the set of baseline operation rules may be configured for specificcomputing nodes, containers, or applications.

In an embodiment, the set of baseline operation rules may be furtherconfigured to identify anomalous operations that have occurred within amonitored environment or may be used to filter anomalous operations fromoccurring within the monitored environment. For instance, the set ofbaseline operation rules may be configured to generate specific alertswhen operation input or output triggers an anomaly based on the set ofbaseline operation rules. For example, an alert may be generated when acontainer reads a file that is included within the set of baseline filesdefined in a specific rule. The set of baseline operation rules may alsobe configured as a filter to be used within a kernel of a computingnode. For example, kernel 205 within computing node 105 may beconfigured to implement the set of baseline operation rules as ananomaly exception filter that prevents anomalous operations fromexecution. For instance, if an operation requests opening a specificfile that is not part of the set of baseline files defined in thespecific rule, then the kernel 205 may prevent the operation fromexecuting. In an embodiment, usage configurations for the set ofbaseline operation rules may be stored within the rules repository 160.

The rule generation instructions 140 may provide instruction toautomatically update existing sets of baseline operation rules basedupon the elements in the aggregated baseline dataset. In an embodiment,the aggregated baseline dataset may be based on operations related to aspecific application or container to which generated rules alreadyexist. In this scenario, elements of the aggregated baseline dataset maybe used to update the existing rules stored in the rules repository 160.Updates may include modifying sets of expected input or output for oneor more element properties. By allowing baseline operation rules to beupdated based upon new operation information. The baseline operationrules may be tailored to the latest operations and interactionsoccurring on applications and containers of interest.

Referring back to FIG. 3, step 335 depicts transmitting a set ofbaseline operation rules to a computing node. In an embodiment, theoperation detection system 170 accesses and transmits a set of baselineoperation rules 180 from the rule repository 160 to one or more agents,such as agent 107 residing on computing node 105, for the purposes ofdetecting anomalous operations executing on computing node 105. Theoperation detection system 170 may be configured to transmit the set ofbaseline operation rules 180 that include configuration options fortriggering alerts when an anomalous operation occurs within thecomputing node 105 and for filtering particular anomalous operationsfrom occurring on the computing node 105.

In an embodiment, the agent 107 may be configured to receive the set ofbaseline operation rules 180 and implement rule-based activitymonitoring that monitors activity between the kernel 205 and the one ormore running applications and containers interacting with the kernel205. For example, the set of baseline operation rules 180 may include,but are not limited to, rules that define expected system calloperations, operation parameters, and output from requested operations.The agent 107 may monitor activity between the containers 225 and 235,applications 215, 220, 227, and 237, and the kernel 205 to determinewhether any requested operations include property values that are notdefined within the set of baseline operation rules 180. If an operationcontains property values not defined within a specific rule, then theagent 107 may determine that the operation is an anomaly and maygenerate an alert. In an embodiment, the alert may be transmitteddirectly to a system administrator account or a user account, or may betransmitted to the operation detection system 170. In an embodiment,alerts transmitted to the operation detection system 170 may be storedand transmitted to one or more users or administrators. Stored alertsmay be stored within the rules repository 160 for the purpose ofanalyzing trends and updating existing rules depending on whether theanomalous operations are frequently occurring and whether the propertyvalues should be considered part of the expected values.

In an embodiment, user feedback may be used to update the set ofbaseline operation rules 180. The agent 107 may be configured to, upondetecting an anomalous operation, generate an interactive event messagethat is displayed to the current user. For example, if a user isinteracting with container 225 and the agent 107 detects an anomalousoperation from container 225, then the agent 107 may generate a pop-upmessage or other type of notification that is displayed to the user. Themessage may include a user interface that allows the user to select fromoptions that include, but are not limited to, acknowledging the eventmessage, flagging the event message as being inaccurate, and temporarilyallowing the anomalous operation associated with the event message.Additionally, the user feedback may also include a user-inputted scorethat is assigned as an accuracy value for the rule used to flag theanomalous operation. For example, if an operation was identified asanomalous, then the user may be presented with a message that indicatesthe anomalous operation identified and the rule used to identify theoperation. The user may then select an option that confirms the detectedanomalous operation and the user may assign an accuracy score to therule used to detect the anomalous operation.

In an embodiment, flagging the event message as inaccurate may triggerthe agent 107 to transmit the user feedback to the operations detectionsystem 170. The operations detection system 170 may be configured toincorporate user feedback sent from the agent 107 into the rulegeneration by updating the specific rules that incorrectly flaggedoperations as anomalous. Updating of the rules may include convertingthe feedback into an adjustment score that may be inputted into step 320to update existing scores of elements of the aggregated baseline.

In an embodiment, the set of baseline operation rules 180 may comprisesubsets of baseline operation rules tailored to specific containers andapplications running on the computing node 105. For example, referringto FIG. 2, the set of baseline operation rules 180 may include subsetsof baseline operation rules specific to monitoring operations from eachof the applications 215, 220, 227, and 237, and the containers 225 and235. Each of the subsets of baseline operation rules may be based onspecific aggregated baselines compiled from operations from each of theapplications 215, 220, 227, and 237, and the containers 225 and 235.

In an embodiment, subsets of the set of baseline operation rules 180 mayinclude baseline operation rules that are based upon parameter templatedefinitions. The agent 107 may be configured to incorporatecustomizations of applications and containers by interpretingconfiguration files, command line parameters, environment variables, andany other mechanism used to customize an application and container.Customization information may then be incorporated by the parametertemplate definitions in order to incorporate customized baselineoperation rules.

In an embodiment, the set of baseline operation rules may includesubsets of baseline operation rules generated from different aggregatedbaselines. For example, a first subset of baseline operation rules maybe based on an aggregated baseline derived from operations fromcontainer-A and a second subset of baseline operation rules may be basedon an aggregated baseline derived from operations from container-B. Ifcontainer-A is a container image that is instantiated within an image ofcontainer-B, then the set of baseline operation rules used to monitoroperations for container-A may include the first subset of baselineoperation rules and an inherited subset of baseline operation rulesbased on the second subset of baseline operation rules. For examplereferring to FIG. 2, multiple subsets of baseline operation rules may beused to monitor application 227, which is running within container 225.In this scenario, the baseline operation rules used to monitorapplication 227 may include a subset specific to application 227 andanother subset that is inherited from the container 225. By compiling acomplete set of usable baseline operation rules from rules specific tothe application and rules inherited from the environment that theapplication is running in, the set of usable baseline operation rulesmay be customized to monitor values of properties of operations specificto a target application and properties of operations specific to theunique environment in which the target application is running. Anotherexample of using multiple subsets of baseline operation rules includeincorporating baseline rules that may be specific to a particularoperating system with a specific application. For instance, if container235 is running an image of the Linux operating system Ubuntu andapplication 237 is running within container 235, then subsets ofbaseline operation rules may be used to monitor operations fromapplication 237 that include a subset of specific rules generated forapplication 237 and a subset of specific rules that are relevant to theUbuntu operating system. Additionally, if container 235 implemented animage of the Windows operating system, then monitoring application 237may include using baseline operation rules specific to application 237and baseline operation rules specific to the Windows operating system.

In an embodiment, an agent may use the set of baseline operation rulesto filter out anomalous operations from being executed. Referring backto FIG. 2, agent 107 may be configured to implement filtering triggersbased upon the set of baseline operation rules 180 received from theoperations detection system 170. Agent 107 may use exception handlingmechanisms to catch operations flagged as anomalies and filter them outby preventing execution of the operations. For instance, agent 107 mayuse tracepoints within the kernel module 210 to identify property valuesof anomalous operations based upon the set of baseline operation rules180, and within the tracepoints, force the particular operation to fail,thus preventing the operation from executing.

In another embodiment, the set of baseline operation rules may be usedto filter out anomalous operations by integrating the set of baselineoperation rules into the operating system's existing filteringmechanisms. For example, the set of baseline operation rules may beintegrated into a network filtering framework such as Netfilter orintegrated into SELinux for I/O and process execution filtering.

In an embodiment, configuration of monitoring rules based on thereceived set of baseline operation rules may be configured usingcontainer management systems and orchestrators. Different orchestratorsmay include commercial implementations such as Kubernetes and Mesos,which may be used to extract metadata useful for configuring how agent107 uses the set of baseline operation rules 180 received from theoperations detection system 170. For example, orchestrator configurationfiles may used to configure the extent to which the agent uses the setof baseline operation rules 180 for monitoring operations. In anembodiment, the agent 107 may be configured to read the orchestratorconfiguration files and based on the orchestrator configuration, theagent 107 may configure monitoring of operations. In another embodiment,the agent 107 may be configured from an orchestrator user interface,where a user may customize which baseline operation rules are enforcedbased upon the desired monitoring level. For example, if a user intendsto restrict access of incoming requests, then the user may use theorchestrator to configure the agent 107 to only allow requests from aspecific port, such as port 80. Additionally, the agent 107 may beconfigured to implement different rules based upon the desired runtimeenvironment. For example, the agent 107 may be configured to monitoroperations based on a subset of baseline operation rules for aproduction environment, a quality assurance environment, and a developerenvironment, where each environment enforces a different set of rulesfrom the set of baseline operation rules 180.

5. Implementation Example—Hardware Overview

According to one embodiment, the techniques described herein areimplemented by one or more special-purpose computing devices. Thespecial-purpose computing devices may be hard-wired to perform thetechniques, or may include digital electronic devices such as one ormore application-specific integrated circuits (ASICs) or fieldprogrammable gate arrays (FPGAs) that are persistently programmed toperform the techniques, or may include one or more general purposehardware processors programmed to perform the techniques pursuant toprogram instructions in firmware, memory, other storage, or acombination. Such special-purpose computing devices may also combinecustom hard-wired logic, ASICs, or FPGAs with custom programming toaccomplish the techniques. The special-purpose computing devices may bedesktop computer systems, portable computer systems, handheld devices,networking devices or any other device that incorporates hard-wiredand/or program logic to implement the techniques.

For example, FIG. 4 is a block diagram that illustrates a computersystem 400 upon which an embodiment of the invention may be implemented.Computer system 400 includes a bus 402 or other communication mechanismfor communicating information, and a hardware processor 404 coupled withbus 402 for processing information. Hardware processor 404 may be, forexample, a general purpose microprocessor.

Computer system 400 also includes a main memory 406, such as a randomaccess memory (RAM) or other dynamic storage device, coupled to bus 402for storing information and instructions to be executed by processor404. Main memory 406 also may be used for storing temporary variables orother intermediate information during execution of instructions to beexecuted by processor 404. Such instructions, when stored innon-transitory storage media accessible to processor 404, rendercomputer system 400 into a special-purpose machine that is customized toperform the operations specified in the instructions.

Computer system 400 further includes a read only memory (ROM) 408 orother static storage device coupled to bus 402 for storing staticinformation and instructions for processor 404. A storage device 410,such as a magnetic disk, optical disk, or solid-state drive is providedand coupled to bus 402 for storing information and instructions.

Computer system 400 may be coupled via bus 402 to a display 412, such asa cathode ray tube (CRT), for displaying information to a computer user.An input device 414, including alphanumeric and other keys, is coupledto bus 402 for communicating information and command selections toprocessor 404. Another type of user input device is cursor control 416,such as a mouse, a trackball, or cursor direction keys for communicatingdirection information and command selections to processor 404 and forcontrolling cursor movement on display 412. This input device typicallyhas two degrees of freedom in two axes, a first axis (e.g., x) and asecond axis (e.g., y), that allows the device to specify positions in aplane.

Computer system 400 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic which in combination with the computer system causes orprograms computer system 400 to be a special-purpose machine. Accordingto one embodiment, the techniques herein are performed by computersystem 400 in response to processor 404 executing one or more sequencesof one or more instructions contained in main memory 406. Suchinstructions may be read into main memory 406 from another storagemedium, such as storage device 410. Execution of the sequences ofinstructions contained in main memory 406 causes processor 404 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “storage media” as used herein refers to any non-transitorymedia that store data and/or instructions that cause a machine tooperate in a specific fashion. Such storage media may comprisenon-volatile media and/or volatile media. Non-volatile media includes,for example, optical disks, magnetic disks, or solid-state drives, suchas storage device 410. Volatile media includes dynamic memory, such asmain memory 406. Common forms of storage media include, for example, afloppy disk, a flexible disk, hard disk, solid-state drive, magnetictape, or any other magnetic data storage medium, a CD-ROM, any otheroptical data storage medium, any physical medium with patterns of holes,a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 402. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 404 for execution. For example,the instructions may initially be carried on a magnetic disk orsolid-state drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 400 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 402. Bus 402 carries the data tomain memory 406, from which processor 404 retrieves and executes theinstructions. The instructions received by main memory 406 mayoptionally be stored on storage device 410 either before or afterexecution by processor 404.

Computer system 400 also includes a communication interface 418 coupledto bus 402. Communication interface 418 provides a two-way datacommunication coupling to a network link 420 that is connected to alocal network 422. For example, communication interface 418 may be anintegrated services digital network (ISDN) card, cable modem, satellitemodem, or a modem to provide a data communication connection to acorresponding type of telephone line. As another example, communicationinterface 418 may be a local area network (LAN) card to provide a datacommunication connection to a compatible LAN. Wireless links may also beimplemented. In any such implementation, communication interface 418sends and receives electrical, electromagnetic or optical signals thatcarry digital data streams representing various types of information.

Network link 420 typically provides data communication through one ormore networks to other data devices. For example, network link 420 mayprovide a connection through local network 422 to a host computer 424 orto data equipment operated by an Internet Service Provider (ISP) 426.ISP 426 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the“Internet” 428. Local network 422 and Internet 428 both use electrical,electromagnetic or optical signals that carry digital data streams. Thesignals through the various networks and the signals on network link 420and through communication interface 418, which carry the digital data toand from computer system 400, are example forms of transmission media.

Computer system 400 can send messages and receive data, includingprogram code, through the network(s), network link 420 and communicationinterface 418. In the Internet example, a server 440 might transmit arequested code for an application program through Internet 428, ISP 426,local network 422 and communication interface 418.

The received code may be executed by processor 404 as it is received,and/or stored in storage device 410, or other non-volatile storage forlater execution.

In the foregoing specification, embodiments of the invention have beendescribed with reference to numerous specific details that may vary fromimplementation to implementation. The specification and drawings are,accordingly, to be regarded in an illustrative rather than a restrictivesense. The sole and exclusive indicator of the scope of the invention,and what is intended by the applicants to be the scope of the invention,is the literal and equivalent scope of the set of claims that issue fromthis application, in the specific form in which such claims issue,including any subsequent correction.

What is claimed is:
 1. A data processing method comprising: creating andstoring, in digital data storage, a score threshold value that isassociated with determining whether a baseline operation rule is to begenerated; receiving, from one or more service monitoring processes thatare executing on one or more computer systems, datasets of operationsthat have been performed on digital objects by one or more processesassociated with one or more computer applications executing on the oneor more computer systems, each dataset of the datasets of operationscomprising a set of operations data representing records of operationsthat were performed by one or more particular processes associated witha particular computer application of the one or more computerapplications; aggregating operations represented in the datasets ofoperations and identifying operation properties from the aggregatedoperations to generate an aggregated baseline dataset that representsoperation properties identified from aggregated operations that aregrouped by common identifiers associated with the operations; assigningscore values to each of the operation properties in the aggregatedbaseline dataset, wherein each assigned score value represents whether aparticular operation property is a candidate for generating a rule thatdefines one or more expected values for the particular operationproperty; automatically generating a set of baseline operations rulesfor only those operation properties in the aggregated baseline datasetthat have assigned values that exceed the score threshold value, the setof baseline operations rules generated based on past successes indetecting operation anomalies.
 2. The data processing method of claim 1,further comprising based on the set of baseline operation rules orfiltering triggers, preventing the operations with operation anomaliesfrom being executed.
 3. The data processing method of claim 1, furthercomprising flagging the operations with operation anomalies andpreventing the flagged operations from being executed.
 4. The dataprocessing method of claim 3, further comprising: flagging theoperations with operation anomalies based on property values of theoperations with anomalous operations; preventing the flagged operationsfrom being executed by forcing the flagged operations to fail.
 5. Thedata processing method of claim 4, further comprising identifyingproperty values of the operation with anomalous operations usingtracepoints.
 6. The data processing method of claim 1, furthercomprising the automatically generating a set of baseline operationsrules for the set of baseline operations rules being programmed todetect anomalous operations that contain unexpected operation propertyvalues.
 7. The data processing method of claim 1, further comprisingemploying past failed detections of operation anomalies to increase thescore threshold value.
 8. The data processing method of claim 1, furthercomprising generating the score threshold value based on a historicalscore threshold value.
 9. The data processing method of claim 1, furthercomprising organizing records of operations in the datasets ofoperations, in groups based on how objects associated with the recordsof operations have been accessed.
 10. The data processing method ofclaim 1, further comprising, prior to aggregating operations representedin the datasets of operations, receiving metadata that is configured toidentify common attributes in operations from the datasets ofoperations, wherein the metadata comprises at least one of: host names,user tags, cloud service provider instance tags, container names,container identifiers, container labels, container image names,container image identifiers, orchestrator labels, and orchestratorannotations.
 11. A computer system comprising: one or more processors;and one or more non-transitory computer-readable storage media coupledto the one or more processors and storing instructions which, whenexecuted by the one or more processors, cause the one or more processorsto execute: creating and storing, in digital data storage, a scorethreshold value that is associated with determining whether a baselineoperation rule is to be generated; receiving, from one or more servicemonitoring processes that are executing on one or more computer systems,datasets of operations that have been performed on digital objects byone or more processes associated with one or more computer applicationsexecuting on the one or more computer systems, each dataset of thedatasets of operations comprising a set of operations data representingrecords of operations that were performed by one or more particularprocesses associated with a particular computer application of the oneor more computer applications; aggregating operations represented in thedatasets of operations and identifying operation properties from theaggregated operations to generate an aggregated baseline dataset thatrepresents operation properties identified from aggregated operationsthat are grouped by common identifiers associated with the operations;assigning score values to each of the operation properties in theaggregated baseline dataset, wherein each assigned score valuerepresents whether a particular operation property is a candidate forgenerating a rule that defines one or more expected values for theparticular operation property; automatically generating a set ofbaseline operations rules for only those operation properties in theaggregated baseline dataset that have assigned values that exceed thescore threshold value, the set of baseline operations rules generatedbased on past successes in detecting operation anomalies.
 12. Thecomputer system of claim 11, the one or more storage media furtherstoring instructions which, when executed by the one or more processors,cause, based on the set of baseline operation rules or filteringtriggers, preventing the operations with operation anomalies from beingexecuted.
 13. The computer system of claim 11, the one or more storagemedia further storing instructions which, when executed by the one ormore processors, cause flagging the operations with operation anomaliesand preventing the flagged operations from being executed.
 14. Thecomputer system of claim 13, the one or more storage media furtherstoring instructions which, when executed by the one or more processors,cause: flagging the operations with operation anomalies based onproperty values of the operations with anomalous operations; preventingthe flagged operations from being executed by forcing the flaggedoperations to fail.
 15. The computer system of claim 14, the one or morestorage media further storing instructions which, when executed by theone or more processors, cause identifying property values of theoperation with anomalous operations using tracepoints.
 16. The computersystem of claim 11, the one or more storage media further storinginstructions which, when executed by the one or more processors, causeautomatically generating a set of baseline operations rules for the setof baseline operations rules by detecting anomalous operations thatcontain unexpected operation property values.
 17. The computer system ofclaim 11, the one or more storage media further storing instructionswhich, when executed by the one or more processors, cause detectinganomalous operations that contain unexpected operation property values.18. The computer system of claim 11, the one or more storage mediafurther storing instructions which, when executed by the one or moreprocessors, cause employing past failed detections of operationanomalies to increase the score threshold value.
 19. The computer systemof claim 11, the one or more storage media further storing instructionswhich, when executed by the one or more processors, cause generating thescore threshold value based on a historical score threshold value. 20.The computer system of claim 11, the one or more storage media furtherstoring instructions which, when executed by the one or more processors,cause organizing records of operations in the datasets of operations, ingroups based on how objects associated with the records of operationshave been accessed.